Queue Based Processing

Flow is a classical middleware. That is, it addresses the problem of a system having to be aware of every other consumer of its data.

Flow sits across several points of an ecosystem:

  • It is a service bus, able to listen on arbitrary paths of the port on which it is listening.
  • In deference to the popularity of the Single Page Application, it acts as a web server, serving web resources which can call back to those paths for data specific to the logged in user session.
  • Flow is a scripting host, allowing complex decisions to be applied to data as they are processed.
Even though is it deployed in a SaaS context, Flow is best operated in a shared custody model. Users are expected to take over content and logic management over time, working from the implemented solutions which are fully visible as source code and configuration in their instance.